Systems and Methods for Reliable Transmission Over Network Resources

ABSTRACT

A method includes receiving a first assignment for a first transmission with a first hybrid automatic repeat request (HARQ) process identifier (process ID) in a first network resource, receiving a second assignment for a second transmission with a second HARQ process ID in a second network resource, wherein the first network resource and the second network resource differ in a domain other than a time domain, detecting an indication indicating that the first HARQ process ID and the second HARQ process ID map to a same transmission block (TB), and communicating with an access node, a transmission associated with at least one of the first HARQ process ID or the second HARQ process ID.

This application is a continuation of U.S. patent application Ser. No.16/231,006, filed on Dec. 21, 2018, entitled “Systems and Methods forReliable Transmission Over Network Resources,” which claims the benefitof U.S. Provisional Application No. 62/616,390, filed on Jan. 11, 2018,entitled “Systems and Methods for Reliable Transmission Over a CarrierGroup,” applications of which are hereby incorporated herein byreference in their entireties.

TECHNICAL FIELD

The present disclosure relates to systems and methods for reliabletransmission over network resources.

BACKGROUND

Existing technologies such as multi-antenna, repetition/slotaggregation, low modulation and coding scheme (MCS), and hybridautomatic repeat request (HARQ) procedures have been considered aspossible ways to enhance reliability or diversity. However, theseapproaches are conventionally performed within a single carrier.Drawbacks of single carrier implementations include:

-   -   difficult to ensure reliable quality of service (QoS) in a        band-limited carrier, time-domain repetition or multiple HARQ        transmission may increase latency;    -   difficult to ensure reliability when user equipment (UE) loading        is high in a given carrier, where UEs receive/transmit critical        communications with low latency;    -   difficult to exploit frequency diversity (in a band-limited        carrier) when during an interval, critical common signaling such        as synchronization sequence block (SSB) are transmitted;        co-located multiple-input multiple-output (MIMO) may suffer from        correlated fading; and    -   HARQ retransmissions may not be feasible for several slots or        subframes on an unlicensed component carrier (CC) due to the        activity of coexisting nodes/systems in proximity.

Carrier domain can be exploited for flexible and efficient resourcesharing for data duplication. This can be performed across frequencydivision duplex (FDD) carriers, time division duplex (TDD) carriers,unlicensed carriers, high frequency/low frequency carriers. Two existingframeworks for carrier domain resource sharing, where multiple carriersare used for communication between the network and a UE, includedual-connectivity and carrier aggregation.

In the dual-connectivity framework, there is a different media accesscontrol (MAC) entity for each carrier group. Transport block (TB)scheduling for a UE is performed independently on the each carriergroup. The carrier aggregation framework has one MAC entity for allcarriers, but TBs are still scheduled separately/independently on themultiple carriers. The carrier aggregation framework may be used toenhance data rate. With the carrier aggregation framework, the MACentity schedules independent HARQ processes on each carrier.

Data duplication at the packet data convergence protocol (PDCP) layercan be performed to produce multiple TBs from one TB for transmission onseparate carriers, but the multiple TBs then pass through the separateMAC entities (for dual-connectivity) or a single MAC entity (carrieraggregation) and are scheduled independently in both cases. The UEtreats the received TBs independently. TB retransmissions are scheduledon the same carrier as original data TB transmissions.

The protocol stack for legacy carrier aggregation is depicted in FIG. 1, and is based on single MAC with separate HARQ entities per componentcarrier. A HARQ entity is the combination of the HARQ transmit/receivebuffers of the associated HARQ processes handled by the HARQ entity, andtheir corresponding HARQ state machines.

If the same TB (more generally the same TB or different redundancyversions of the same TB) is repeated in another component carrier, theUE needs to identify that to be the case. The protocol stack in FIG. 1includes a radio link control (RLC) layer 100, MAC layer 102, andphysical (PHY) layer 104. The RLC layer 100 includes multiple RLCentities 110,112,114 that receive TBs from the PDCP layer (not shown).In the MAC layer 102, multiplexing 116 takes place, and then separateHARQ entities 118,120 generate TBs for each of two component carriersCC1, CC2 in the PHY layer 104.

In some systems, transmissions are performed on component carriers inunlicensed spectrum, e.g., in New Radio (NR)-Unlicensed (NR-U) usingCA,DC, or stand-alone (SA) modes). In such systems, the gnodeB (gNB)/UEmay not be able to gain medium access on the original band to performthe HARQ retransmission for several slots or subframes due to thefailure of the regulatory-required listen-before-talk (LBT) procedure.Furthermore, wide-band transmissions, e.g., carrier-wide transmissions,are desired in NR-U to shorten the channel occupancy time and todecrease the power spectral density, whereas LBT failure can be causedby a full or partial occupancy of the LBT bandwidth by the coexistingnodes/systems.

With asynchronous HARQ, a retransmission might not occur for severalslots or subframes due to a blocked or lost acknowledgement(ACK)/negative acknowledgement (NACK) feedback transmission as a resultof LBT failure or persistent collisions with the transmissions of hiddennodes on that unlicensed component carrier.

Moreover, the receiving end RLC layer will not request a retransmissionof the associated SDU from the sending end RLC layer unless a subsequentSDU has been received and a reordering timer has been started andelapsed. The sending end RLC then triggers the retransmission of the SDUand new associated TBs are created and scheduled at the MAC entity,possibly on a different component carrier.

Significant delays and throughput reduction can be incurred with such adesign in unlicensed spectrum. There is a need for efficientLBT-resilient mechanisms for performing the HARQ retransmissions andtransmission of the associated ACK/NACK feedback on a PUCCH inunlicensed spectrum.

SUMMARY

Example embodiments provide systems and methods for reliabletransmission over a network resource.

In accordance with an example embodiment, a computer-implemented methodis provided. The computer-implemented method includes receiving, by auser equipment (UE), a first assignment for a first transmission with afirst hybrid automatic repeat request (HARQ) process identifier (processID) in a first network resource, receiving, by the UE, a secondassignment for a second transmission with a second HARQ process ID in asecond network resource, wherein the first network resource and thesecond network resource differ in a domain other than a time domain,detecting, by the UE, an indication indicating that the first HARQprocess ID and the second HARQ process ID map to a same transmissionblock (TB), and communicating, by the UE, with an access node, atransmission associated with at least one of the first HARQ process IDor the second HARQ process ID.

Optionally, in any of the preceding embodiments, an embodiment whereincommunicating the transmission comprises receiving, by the UE, thetransmission from the access node.

Optionally, in any of the preceding embodiments, an embodiment whereincommunicating the transmission comprises transmitting, by the UE, thetransmission to the access node.

Optionally, in any of the preceding embodiments, an embodiment whereinthe first network resource and the second network resource include atleast one of a frequency resource, a time-frequency resource, a coderesource, a spatial resource, a carrier, a component carrier, a cell, ora bandwidth part (BWP).

Optionally, in any of the preceding embodiments, an embodiment whereinthe first network resource and the second network resource areassociated with different transmission/receiving points (TRP).

Optionally, in any of the preceding embodiments, an embodiment whereinthe first HARQ process ID and the second HARQ process ID are the same.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication is a semi-static configuration.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication is a combination of a semi-static configuration anddynamic signaling.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises:

-   -   an indication indicating that a pool of HARQ process IDs are        common across at least the first and second network resources,        wherein the first HARQ process ID and the second HARQ process ID        are the same to indicate that the first and second HARQ process        IDs map to the TB.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises an indication indicating that a subset of apool of HARQ process IDs are common across at least the first and secondnetwork resources, wherein the first HARQ process ID and the second HARQprocess ID are the same and belong to the subset to indicate that thefirst and second HARQ process IDs map to the TB.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises an indication indicating that a subset of apool of HARQ process IDs are common across a subset of a set of networkresources, wherein the first and second HARQ process IDs are the sameand belong to the subset of the pool and the first and second networkresources belong to the subset of the set of network resources toindicate that the first and second HARQ process IDs map to the TB.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises a field in the second assignment indicatingthat the second assignment is in respect of a retransmission of the TB.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises a semi-static configuration that associates thesecond HARQ process ID with the first HARQ process ID, such that thefirst assignment including the first HARQ process ID, the secondassignment including the second HARQ process ID, and the field in thesecond assignment together indicate that the first and second HARQprocess IDs map to the TB.

Optionally, in any of the preceding embodiments, an embodiment whereinfor the first assignment and the second assignment to be in respect ofthe same TB, the first assignment and the second assignment are receivedwithin a specified time window of one another.

Optionally, in any of the preceding embodiments, an embodiment whereinthe specified time window is specified in terms of a number of timeslots, mini-slots, subframes, or symbols.

Optionally, in any of the preceding embodiments, an embodiment whereinreceiving the first assignment and the second assignment comprisesreceiving a single downlink control information (DCI).

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises a first field in the first assignmentindicating that there will be an assignment in respect to the TB on adifferent network resource, and a second field in the second assignmentindicating that the second assignment is in respect to the TBtransported on the different network resource.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication further comprises at least one semi-statically configuredmapping rule that associates the first HARQ process ID on the firstnetwork resource with the second HARQ process ID on the second networkresource, and wherein the first assignment including the first field andthe second assignment including the second field together indicate thatthe first and second assignments are in respect to the TB only when thefirst HARQ process ID is associated with the second HARQ process IDthrough the at least one mapping rule.

Optionally, in any of the preceding embodiments, an embodiment whereincommunicating a transmission associated with at least one of the firstHARQ process ID or the second HARQ process ID comprises receiving afirst transmission associated with the first HARQ process ID on thefirst network resource and receiving a second transmission associatedwith the second HARQ process ID on the second network resource.

Optionally, in any of the preceding embodiments, an embodiment furthercomprising processing, by the UE, the first transmission to produce afirst set of log likelihood ratios (LLRs), processing, by the UE, thesecond transmission to produce a second set of LLRs, combining, by theUE, the first set of LLRs and the second set of LLRs to produce acombined set of LLRs, and decoding, by the UE, the TB transmitted in thefirst transmission and the second transmission in accordance with thecombined set of LLRs.

Optionally, in any of the preceding embodiments, an embodiment whereinthe HARQ codebook configuration indicates an ACK/NACK resource fortransmitting an ACK/NACK in respect to the TB or versions of the TBreceived over multiple network resources.

Optionally, in any of the preceding embodiments, an embodiment furthercomprising receiving a HARQ codebook configuration indicatingacknowledgement/negative acknowledgment (ACK/NACK) resources used fortransmitting an ACK/NACK in respect to the TB or versions of the TBreceived over multiple network resources.

Optionally, in any of the preceding embodiments, an embodiment furthercomprising transmitting, by the UE, ACK/NACK feedback only on the firstnetwork resource.

Optionally, in any of the preceding embodiments, an embodiment furthercomprising transmitting, by the UE, ACK/NACK feedback on the firstnetwork resource and the second network resource.

Optionally, in any of the preceding embodiments, an embodiment whereinthe first network resource is an unlicensed network resource.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises at least one parameter upon which the UEdetermines whether a switch from the first HARQ process ID on the firstnetwork resource to the second HARQ process ID on the second networkresource has occurred.

Optionally, in any of the preceding embodiments, an embodiment whereinthe first assignment comprises a first TB size indicator indicating asize of the first TB and a first new data indicator (NDI), wherein thesecond assignment comprises a second indicator indicating the size ofthe second TB and a second NDI, wherein the first assignment and thesecond assignment indicate the same TB size, and wherein the first NDIand the second NDI are the same.

Optionally, in any of the preceding embodiments, an embodiment whereinthe second assignment comprises an indicator indicating at least one ofan identifier of the first network resource or the first HARQ processID.

Optionally, in any of the preceding embodiments, an embodiment whereinthe at least one parameter comprises a timeout value of a timerinitialized by the UE after a HARQ round trip time (RTT) timer elapsesfrom a last transmission in respect to the TB on the first networkresource, such that the timer elapsing indicates a subsequenttransmission in respect to the TB will occur on a different networkresource.

Optionally, in any of the preceding embodiments, an embodiment whereinthe RTT timer elapsing further indicates to the UE to trigger the accessnode to send the second assignment for the transmission of the TB withthe second HARQ process ID in the second network resource.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication further comprises at least one mapping, rule, orparameter in respect to a rule that associates the second HARQ processID with the first HARQ process ID.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication further comprises a semi-statically configuredassociation between the first HARQ process ID and the second HARQprocess ID.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises an index offset indicating a binary indexoffset between the first and second HARQ process IDs.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises a number of binary shifts between the first andsecond HARQ process IDs.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises an index indicating a binary offset and anumber of binary shifts that together associate the second HARQ processID with the first HARQ process ID.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises an index indicating a number of binary shifts,and wherein a binary offset and the number of binary shifts togetherassociate the second HARQ process ID with the first HARQ process ID.

Optionally, in any of the preceding embodiments, an embodiment whereinthe indication comprises an index indicating a binary offset and anumber of binary shifts that together with a semi-statically configuredrule or formula associate the second HARQ process ID with the first HARQprocess ID.

In accordance with an example embodiment, a computer-implemented methodis provided. The computer-implemented method includes receiving, by aUE, a first assignment for a first transmission with a first HARQprocess identifier (process ID) in a first network resource, receiving,by the UE, a second assignment for a second transmission with a secondHARQ process ID in a second network resource, wherein the first HARQprocess ID differs from the second HARQ process ID, detecting, by theUE, an indication indicating that the first HARQ process ID and thesecond HARQ process ID map to a same TB, and communicating, by the UE,with an access node, a transmission associated with at least one of thefirst HARQ process ID or the second HARQ process ID.

In accordance with an example embodiment, a UE is provided. The UEincludes a non-transitory memory storage comprising instructions, andone or more processors in communication with the memory storage. The oneor more processors execute the instruction to receive a first assignmentfor a first transmission with a first HARQ process identifier (processID) in a first network resource, receive a second assignment for asecond transmission with a second HARQ process ID in a second networkresource, wherein the first network resource and the second networkresource differ in a domain other than a time domain, detect anindication indicating that the first HARQ process ID and the second HARQprocess ID map to a same TB, and communicate, with an access node, atransmission associated with at least one of the first HARQ process IDor the second HARQ process ID.

In accordance with an example embodiment, a UE is provided. The UEincludes a non-transitory memory storage comprising instructions, andone or more processors in communication with the memory storage. The oneor more processors execute the instruction to receive a first assignmentfor a first transmission with a first HARQ process identifier (processID) in a first network resource, receive a second assignment for asecond transmission with a second HARQ process ID in a second networkresource, wherein the first HARQ process ID differs from the second HARQprocess ID, detect an indication indicating that the first HARQ processID and the second HARQ process ID map to a same TB, and communicate,with an access node, a transmission associated with at least one of thefirst HARQ process ID or the second HARQ process ID.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, and theadvantages thereof, reference is now made to the following descriptionstaken in conjunction with the accompanying drawings, in which:

FIG. 1 depicts a block diagram of a protocol stack for legacy carrieraggregation;

FIG. 2A depicts a block diagram of a protocol stack for carrieraggregation that shares HARQ process IDs across component carriers;

FIG. 2B depicts a block diagram of an example of shared HARQ process IDsacross component carriers;

FIG. 3A depicts a block diagram of a protocol stack for carrieraggregation which includes a separate HARQ entity for each componentcarrier;

FIG. 3B depicts a block diagram of an example of shared and independentHARQ process IDs across 4 CCs;

FIG. 4 depicts a block diagram of another example of shared andindependent HARQ process IDs across 4 CCs;

FIG. 5 depicts a block diagram of an example of DCI-based cross-carrierscheduling for two component carriers;

FIG. 6 depicts a block diagram of another example of DCI-basedcross-carrier scheduling for two component carriers;

FIG. 7 depicts a block diagram of yet another example of DCI-basedcross-carrier scheduling for two component carriers;

FIG. 8 depicts a block diagram of a further example of DCI-basedcross-carrier scheduling for two component carriers;

FIG. 9A depicts a block diagram of an example of using one DCI toschedule over multiple component carriers;

FIG. 9B depicts a block diagram of another example of using one DCI toschedule over multiple component carriers;

FIG. 10 depicts a block diagram of an example of combiningrepetitions/retransmission of a TB over different carriers;

FIG. 11 depicts a block diagram of HARQ codebook configuration;

FIG. 12 depicts a block diagram of a system for transmission overunlicensed spectrum;

FIG. 13 depicts a block diagram of a system for transmission overunlicensed spectrum showing additional steps that may be implementedfollowing successful TB decoding in the receiver;

FIG. 14A depicts a table which maps a main HARQ Process ID topre-configured auxiliary HARQ Process ID(s);

FIG. 14B depicts a block diagram of an example of an index offset usedto indicate the auxiliary HARQ Process ID;

FIG. 14C depicts a block diagram of an example of binary ID shifts usedto indicate the auxiliary HARQ Process ID;

FIG. 15A illustrates a flow diagram of example operations occurring inan access node;

FIG. 15B illustrates a flow diagram of example operations occurring in aUE;

FIG. 16A illustrates a flow diagram of example operations occurring inan access node transmitting when a network resource becomes blocked;

FIG. 16B illustrates a flow diagram of example operations occurring in aUE receiving when a network resource becomes blocked;

FIG. 17 illustrates an example communication system;

FIGS. 18A and 18B illustrate example devices that may implement themethods and teachings according to this disclosure; and

FIG. 19 is a block diagram of a computing system 1900 that may be usedfor implementing the devices and methods disclosed herein.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The making and using of the disclosed embodiments are discussed indetail below. It should be appreciated, however, that the presentdisclosure provides many applicable inventive concepts that can beembodied in a wide variety of specific contexts. The specificembodiments discussed are merely illustrative of specific ways to makeand use the embodiments, and do not limit the scope of the disclosure.

This application describes solutions where UE receives an assignmentcomprising an indication when same transport block is duplicated ortransmitted in more than one carrier. The UE can be semi-staticallyconfigured for data duplication mode. The assignment can besemi-statically provided to the UE such as configured ID of shared HARQprocess across a carrier group or a subset of carrier group.Alternatively, the assignment can be provided to the UE as a combinationof semi-static and dynamic signaling. In particular, indication can beprovided in one or more of the scheduling downlink control information(DCIs) that schedule same transport block in different carriers. Whenprovided in scheduling DCI, the indication may comprise one or morefields such as a flag for differentiation between duplication orindependent scheduling, HARQ process ID of the other carrier(s) wheredata is duplicated, carrier index of the carrier(s) where data isduplicated. The indication may be provided in one or both of thescheduling DCIs in primary and secondary component carriers. Semi-staticsignaling may notify the UE which set of carriers can be used for dataduplication or which set of HARQ process IDs can be used for duplicationor what is the mapping between a HARQ process ID in one carrier toanother HARQ process ID in a different carrier if data duplication isindicated. In another example, prior semi-static configuration may notbe necessary, and duplication is indicated by dynamic signaling only,i.e., in the form of explicit and/or implicit indication in a DCI.Furthermore, a common HARQ feedback can be generated by the UE, if theUE is able to combine the packets and if the UE is configured for thisprocess. The common HARQ feedback can be transmitted in the primarycomponent carrier (PCC) and/or a secondary component carrier (SCC)uplink configured/indicated resource. Common HARQ feedback generationmay require soft buffer data/log-likelihood ratio (LLR) sharing at thereceiver.

Although the discussion focuses on carriers and carrier groups, acarrier is an example of a network resource and a carrier group is anexample of a group of network resources. In general, a network resourceis a resource of the network that is usable in the transmission ofinformation. A network resource may be characterized as being a memberone or more domains, where the domains include the time domain, thefrequency domain, the code domain, a spatial domain, and so forth.Examples of network resources include time resources, frequencyresources, code resources, spatial resources, time-frequency resources,carriers, component carriers, bandwidth parts, and so on.

As used herein, repetition of a transport block implies subsequenttransmission of a transport block after initial transmission but beforeHARQ feedback, if any. Retransmission implies a subsequent transmissionof a transport block after initial transmission is not correctlyreceived. Below, data duplication is used in the context when the sametransport block, or different redundancy versions of the same transportblock, is transmitted over multiple carriers. Duplication may happen atthe same or different time, in the form of a repetition orretransmission. The UE may or may not be able to do HARQ combining ofthe copies of a transport block transmitted over different carriers,depending on the hardware capability of the UE and/or timing of thetransmissions in different carriers and/or indicated HARQ feedbacktiming.

Methods Using Pre-Configured Shared HARQ Process in a Carrier Group

In a first set of methods, HARQ process are shared across two or morecarriers in a carrier group, and these shared HARQ process arepre-configured, for example, semi-statically using radio resourcecontrol (RRC) signaling on a per UE basis. Once the configuration isperformed/notified to the UE, additional signaling (such as dynamicsignaling in a DCI), on a per transmission basis, is not required toinform a UE of which HARQ Processes are shared and/or which componentcarriers are sharing on or more HARQ Process IDs.

Method 1A: Shared HARQ Process across all carriers in a carrier group

This method depends on configuring/associating a pool of HARQ processacross carriers. Rather than having independent HARQ Process percarrier, a pool of K HARQ process are common across all carriers oracross all carriers in a carrier group. With this approach, multipleHARQ entities share a pool of HARQ process. The pool of HARQ process mayinclude all HARQ process, or a subset of all the HARQ processes.

A UE receiving indication of a given HARQ process ID from more than onecarrier in the pool concludes that a same transmission or transportblock is scheduled across the carriers for which indication is received.In some embodiments, indication of assignment of a HARQ process ID to atransmission or transport block may be provided in a scheduling DCI orphysical downlink control channel (PDCCH). When PDCCH scheduling overdifferent carriers in a group indicates a common HARQ process ID in thesame slot/symbol(s)/interval or within a pre-configured/pre-definedperiod/duration of slots/symbols/intervals, the configured UE concludesthat transmission of same packet is scheduled across the carriers.

A UE can be RRC configured with the association of a pool of HARQprocess IDs and corresponding CC indices of component carriers that areto use the common pool of HARQ processes.

This approach is suitable for a UE that does not require a large numberof HARQ processes supported across component carriers. The number ofavailable HARQ processes does not scale with the number of componentcarriers, in the sense that adding a component carrier that uses acommon set of HARQ processes with another component carrier or carriersdoes not increase the number of available HARQ processes.

An example protocol stack is shown in FIG. 2A, which differs from FIG. 1in that the MAC layer includes HARQ entities 218,220 for componentcarriers CC1,CC2 respectively that are part of a group of HARQ entities230 that shares HARQ processes across component carriers. Note that HARQentities that share HARQ processes may share soft buffer information.

FIG. 2B shows a specific example of shared HARQ process, in which thereare 8 HARQ process with HARQ ID 0, . . . , HARQ ID 7, that are sharedbetween four component carriers CC1, . . . , CC4 configured for a UE.

A first example of TB transmission is indicated at 250, in which fourTBs with different HARQ Process IDs are transmitted on the fourcarriers. These are independent TB transmissions.

A second example of TB transmission is indicated at 252, in which twoTBs with the same HARQ ID 1 are transmitted on two carriers CC1,CC2.These are the same TB or redundancy versions of the same TB. Anindependent TB is transmitted on CC3.

A third example of TB transmission is indicated at 254, in which threeTBs with the same HARQ ID 1 are transmitted on three carriersCC1,CC2,CC3. These are the same TB or redundancy versions of the sameTB.

Method 1B: Shared HARQ Process in a Carrier Group for Some but not allProcess

In a variant of method 1A, some HARQ process are shared across a set ofcomponent carriers, and other process are independently used in eachcomponent carrier.

An example protocol stack is shown in FIG. 3A, which differs from FIG.2A in that the MAC layer includes a separate HARQ entity 300,302 foreach component carrier, but there is cooperation between the two HARQentities 300,302 as indicated at 304, across component carriers.

In mathematical terms, where the maximum number of HARQ process percomponent carrier is K>=1, P HARQ processes are shared across thecomponent carriers, where P<K. Duplication across component carriersuses the pool of P HARQ processes only. Which HARQ process are sharedcan be RRC configured for a UE.

An example is shown in FIG. 3B which shows 8 HARQ processes per cell. Ofthese, HARQ process with HARQ ID 0, . . . , HARQ ID 4 are independentfor each of four component carriers CC1, . . . , CC4, and HARQ ID 5, . .. , HARQ ID 7 are shared across the four component carriers.

A first example of TB transmission is indicated at 350, in which fourTBs with different HARQ Process IDs belonging to the set of independentHARQ Process are transmitted on the four carriers. These are independentTB transmissions.

A second example of TB transmission is indicated at 352, in which twoTBs with the same HARQ ID 5 are transmitted on two carriers CC1,CC2.Because HARQ ID 5 is a shared process, these TBs are duplicates in thatone TB is a duplicate (i.e. repetition or retransmission, same ordifferent redundancy version) of the other TB. An independent TB istransmitted on CC3.

Method 1C: Shared Process in a Subset of Carriers within a Carrier Group

In a variant of the above-described embodiments, HARQ process are sharedacross a subset of the component carriers in a carrier group. All of theHARQ process may be shared across the subset of component carriers (asper the example of FIG. 2A) or a subset of the HARQ Process may beshared across the subset of component carriers (as per the example ofFIG. 3A).

Mathematically, this can be expressed as follows:

-   -   Maximum number of process per component carrier is K=>1;    -   P<K processes are shared across M<N component carriers, where        N=total number of component carriers;    -   such that duplication across component carriers uses the pool of        P processes over M component carriers only.

A specific example is shown in FIG. 4 where there are K=8 HARQ process,P=3 shared HARQ Process, N=4 component carriers, and M=2 componentcarriers that use the shared HARQ Process IDs.

A first example of TB transmission is indicated at 450, in which two TBswith the same HARQ ID 3 are transmitted on two carriers CC1,CC2. BecauseHARQ ID 3 correspond to a shared process between CC1 and CC2, thesetransmissions are the same TB or different redundancy versions of thesame TB. An independent TB is transmitted on CC3 using HARQ ID 4, andanother independent TB is transmitted on CC4 also using HARQ ID 4.

A second example of TB transmission is indicated at 452, in which threeTBs with the same HARQ ID 1 are transmitted on three carriersCC1,CC2,CC3. Because HARQ ID 1 correspond to a shared process betweenCC1 and CC2, the two transmissions on those carriers are the same TB orredundancy versions of the same TB. An independent TB is transmitted onCC3 using the same HARQ ID 1.

For the embodiments of FIGS. 2A,3A,4 , configuration may be performedsemi-statically, for example using radio resource control (RRC)signaling. This can involve signaling one or more of the following:

-   -   Indices of component carriers in a carrier group    -   Indication of which HARQ Process are shared    -   Indication of which component carriers share HARQ Processes.

Once the configuration is performed, additional signaling, on a pertransmission basis, is not required to inform a UE of which HARQ Processare shared and/or which component carriers are sharing one or more HARQProcess. In some embodiments, a dynamic indication (for example in aDCI) is used to indicate which CCs of the pre-configured sharing carriergroup are currently carrying duplications of the same TB.

Methods Using DCI-Based Indication of Mapped HARQ Process ID in aCarrier Group

In a second set of methods, HARQ process IDs are mapped, on a pertransmission basis, across two or more carriers in a carrier group, andthis is indicated to a UE in downlink control information (DCI)transmissions that schedule the TB transmissions using the shared HARQProcess. In some embodiments, as detailed below, DCI signaling indicateswhen the same or different HARQ process ID across different carriers areused for transmission of the same transport block or packet. In otherwords, HARQ process IDs in different carriers do not have to be the samefor the same packet transmission/duplication/repetition/retransmissionin the case of DCI based signaling. For the examples described below,DCI signaling can be conveyed in a scheduling DCI, for example PDCCHcarrying a grant.

Method 2A: Use a Separate DCI on Each Component Carrier

In some embodiments, the DCI-based approach is a unified DCI solutionwhich can support both data duplication and legacy TB scheduling in acarrier aggregation framework. These embodiments will be described inthe context of two component carriers referred to herein as a PCC and aSCC but the approach can be generalized to any two or more componentcarriers generally on a single cell or multiple cells.

In this embodiment, separate HARQ processes are implemented for the twocarriers. Consistent with a legacy carrier aggregation, in someembodiments, a default configuration is used, in which there is noshared HARQ processing. In other words, two TBs transmitted on the twocarriers are independent, irrespective of the HARQ process IDs used onthe two carriers which may be the same or different.

FIG. 5 shows an example of scheduling for two component carriers: DCI 2502 indicates transmission scheduling for the PCC 504, and DCI 1 500indicates transmission scheduling for the SCC 506. HARQ Process IDs inDCI 1 and DCI 2 are independently mapped or correlated, with arelationship between the two DCIs indicated using a flag in a new field,as detailed below. The HARQ IDs for duplicate TB transmissions may bethe same or different, and the same HARQ ID used on two CCs may relateto duplicate or independent TBs.

To achieve independent scheduling, DCI 1 and DCI 2 schedule independentTBs on the two carriers. To achieve data duplication, DCI 1 and DCI 2schedule the same TB on the two carriers. One or more fields in one orboth DCI 1 and DCI 2 are used to indicate whether data duplication isused or not. Various examples are described below.

Note that DCI 1 can be received in the primary component carrier or asecondary component carrier. If DCI 1 is received in PCC and itsscheduled PDSCH and PUCCH is in SCC as shown in FIG. 5 , DCI 1 wouldthen be called a cross-carrier scheduling DCI. If DCI 1 is received inSCC and its scheduled PDSCH and PUCCH is in SCC, then it would be calleda self-scheduling DCI.

To configure data duplication across carriers, a UE needs to identifywhen a TB is duplicated across carriers. One or more of the two DCIs,i.e., self-scheduling DCI of PC, i.e., DCI 2, and self/cross-schedulingDCI of SC (e.g., DCI 1 is a cross-scheduling DCI), include an indicationthat informs the UE of whether data duplication is taking place or not.The indication may comprise one or more fields in one or both of theDCIs. Indication notifies whether signaled HARQ processes carry same ordifferent data in the carriers for which scheduling DCIs are received.

In a specific example, DCI 1 includes a flag (or other indication) thatindicates whether data duplication is taking place or not. With thisapproach, the same DCI format can be used for both independentscheduling or data duplication. For example:

-   -   Flag: 0→legacy CA with independent scheduling,    -   Flag: 1→data duplication. It should be understood that the flag        definitions could be reversed. In addition, it should be        understood that the flag may instead be included in DCI 2 for        PCC. In addition, below, another example is provided in which        there is an additional field in the DCI for both PCC and SCC.

In some embodiments, a single-bit flag can indicate the data duplicationbetween the two DCIs (transmitted simultaneously or with a time gap)only in the absence of any other concurrent DCIs for the same RNTI/UE asdepicted in FIG. 6 and FIG. 7 , described below. In the more generalcase, a single-bit flag might not be sufficient. Example methods ofaddressing this are provided below.

FIG. 5 shows an example set of DCI fields for DCI 1 indicated at 510.The fields include a carrier indicator, HARQ Process ID, and theabove-discussed flag. More generally, the DCI may include differentand/or additional fields (usually including scheduling information suchas resource allocation), and the indicator field may be a flag or afield having a different structure.

With this embodiment, the UE may follow HARQ timing indicated in DCI 2or DCI 1. Independent or same bundling or repetition numbers can beconfigured/indicated for the TB transmissions in different carriers.

Some prior association may or may not be configured in advance, orsemi-statically. A specific relationship between HARQ Process IDs forthe two carriers for data duplication purposes may be configured. Forexample, there may be a configuration that maps HARQ Process ID in DCI 1to HARQ Process ID in DCI 2 or vice versa for data duplication purposeswhen the flag=1 (or more generally, when data duplication is indicated).

In some embodiments, specific UEs can be configured by RRC signaling tosupport the feature.

In a specific example, if HARQ ID i and HARD ID j are received onseparate component carriers with the flag set to duplication mode, {i,j} € {1, . . . , N}:

-   -   The UE may use a configured resource on the PCC (for example on        a physical uplink control channel (PUCCH)) to indicate ACK/NACK        feedback;    -   Alternatively, the UE may duplicate ACK/NACK feedback in the        HARQ feedback resource corresponding to the DCIs in PCC and SCC;    -   Alternatively, the UE will not combine the transmissions, and        the UE will send ACK/NACK in the corresponding HARQ feedback        resources corresponding to the DCIs in PCC and SCC.

In some embodiments, DCI 1 and DCI 2 can be received in the samescheduling period, for example the same transmit time interval (TTI). Inanother embodiment, DCI 2 may precede DCI 1 by n time units, where n maybe a configurable value that can be set, for example by an RRC or DCI orMAC control element (CE). The time units can be symbols or slots.

DCI 1 and DCI 2 can be of the same or different size.

In some embodiments, DCI 1 is a compact DCI that contains at least oneof a field indicating a component carrier, HARQ process ID and a fieldindicating data duplication. In this case, the rest of the fields, suchas resource allocation, are either pre-configured or the sameas/inherited from DCI 2.

In some embodiments, DCI 2 includes a bandwidth part (BWP) index. A BWPmay or may not be indicated in DCI 1.

If a UE is configured for data duplication over a carrier group, the UEcan monitor for a subsequent DCI scheduling the same TB within theactivity period (n time units referred to above).

FIG. 6 shows an example of DCI-based cross-carrier scheduling. DCI 2 istransmitted to schedule on the PC. DCI 1 is transmitted to schedule aduplicate transmission on the SC. DCI 1 can be transmitted, andreceived, simultaneously with DCI 2, or later.

Examples of DCI-Based Cross-Carrier Scheduling

Three examples are shown in FIG. 7 . In the first example 700, a DCI istransmitted on the PCC with HARQ ID 4, and a DCI is transmitted on theSCC with HARQ ID 1, and flag=0, meaning no duplication. The scheduledTBs are treated as two different TBs, consistent with legacytransmission.

In the second example 702, a DCI is transmitted on the PCC with HARQ ID5, and a DCI is transmitted on the SCC with HARQ ID 2, and flag=1,meaning duplication. These scheduled TBs are treated as two copies (orredundancy versions) of the same TB.

In the third example 704, a DCI is transmitted on the PCC with HARQ ID1, and a DCI is transmitted on the SCC with HARQ ID 3 within n timeunits of the DCI on the PC, and flag=1, meaning duplication. Thescheduled TBs are treated as two copies (or redundancy versions) of thesame TB.

There can be an ambiguity as to which TB is being duplicated if multipleTBs are scheduled within the window when the indicator is set toindicate duplication. An example is shown in FIG. 8 . In this example,initial transmissions on PCC are made with HARQ IDs 1 and 2. Within theactivity period, transmissions on the SCC with HARQ IDs 3 and 4, flag=1,are repetitions in respect of the initial transmissions. It is not clearwhich repetition corresponds to which initial transmission.

In some embodiments, to address the possible ambiguity, the PCC DCI alsoincludes an indicator such as a flag that indicates duplication. Then,two DCIs indicating duplication indicate they are scheduling the same TBif they are transmitted within the activity period. If more than one TBneeds data duplication within an activity period, a single bit flag maynot be sufficient to avoid ambiguity. In some embodiments, additionalbits in the indicator can be used to convey which packets areduplications of which packets.

In some embodiments, a predetermined mapping is used. For example, OddID in SCC DCI can be configured to be mapped to Odd ID in PCC DCI, orvice versa. For example:

-   -   IDs in SCC: 2m−1 (with flag=1), 2m (with flag=0), 2m+1 (with        flag=1), 2m+2 (with flag=1) . . . .    -   IDs in PC: 2n−1, 2n, 2n+1, 2n+2

Here, m and n are positive integers.

In some embodiments, a mapping rule can be established as:

2m−1→2n−1, 2m+1→2n+1, 2m+2→2n

In the example above, 2m+2 maps to 2n because 2m was skipped and notused for duplication. Hence, the UE may assume active odd processes withflag 1 in SCC map to the active odd processes in order in the PCC.

In some embodiments, a fallback behavior is configured whereby if a UEmisses one DCI (e.g., PCC DCI), the UE will send ACK/NACK independentlyfor the SCC transmission. Combination of the multiple transmissions bythe UE is not possible in this case.

∈∈≠Alternatively, there can be a pre-configured association between HARQprocesses of the HARQ entities of the PCC and SCC. For example:

-   -   ∈∈≠HARQ i, i={1, 2, . . . , K} in PCC, HARQ j, j={1, 2, . . . ,        M}, in SCC, K, M=>1    -   ∈∈≠HARQ j₁→{i₁, i₂, . . . , i_(Km)}, j₁{1, 2, . . . , M}, i_(p),        i_(q) {1, 2, . . . , K}, i_(p) i_(q), Km<K.

If process j_(i) is scheduled in SCC with flag=1, the UE knows thatprocess j_(i) corresponds to one of processes {i₁, i₂, . . . , i_(Km)}which is scheduled in PCC when or before the DCI for j₁ is received. Themapping procedure can be semi-statically indicated to the UE or obtainedby the UE from a configured look-up table.

Mapping might not be unique for HARQ processes, for efficiency. In thiscase it is up to the network implementation to make sure scheduled HARQprocesses do not conflict when data duplication is indicated.

In this example, a flag or other indication in one or more of thescheduling DCIs is included. A DCI format can be used for this purpose.HARQ process mapping configuration across carriers and/or which carriersare used for duplication can be semi-statically indicated to the UE.

In another example, there may not be any prior association or mappingconfiguration of HARQ process and/or carrier group. One or more ofscheduling DCIs in PCC and SCC(s) may include one or more of: carrierindices of the other carrier(s) where DCI for duplication or same packettransmission is received, HARQ indices which are used in the DCIs sentover other carriers participating in duplication. This indication may bein addition to the carrier index and HARQ process ID indication in theDCI for a given carrier.

Method 2B: Use One DCI to Schedule Over Multiple Component Carriers

In these embodiments, one DCI received in a component carrier schedulesduplicate TBs over multiple carriers. In one example, one HARQ ProcessID and one HARQ timing is indicated. Alternatively, separate HARQProcess ID and same or different HARQ timing is indicated for indicatedcarriers. This DCI format can be received in the PC. The BWP in the SCCmay be associated with for the PCC. In this case, the UE gets duplicateversions of a TB over multiple carriers. Optionally, a Carrier Indicatorfor SCC can be included in the DCI. Optionally, a BWP indicator for SCCor PCC or both is included in the DCI. Other regular fields can beincluded as usual, including fields such as MCS, Resource allocation,multi-antenna indication. Those regular fields can be common fortransmission over multiple carriers, or can be different and explicitlyindicated for different carriers. There can be one set of parameters forboth BWPs or separate sets of parameters for each BWP. The same ordifferent numerologies can be employed for the two transmissions.

For example, in some embodiments, separate resource allocation fieldsare included for the two component carriers. Resource allocation couldbe different for the two component carriers depending on the availableRB indices per carrier. Also, in some embodiments, separate MCS fieldsare included for the two component carriers. The MCS may differ for thetwo component carriers due to the different channel quality across thecarriers.

An example is shown in FIG. 9A which shows a single DCI 900 thatschedules duplicate TBs over a PCC 902 and an SCC 904. FIG. 9B shows anexample where there are associated BWPs in the SCC and the PC.

The DCI format examples discussed above can be received in UE specificsearch space or common search space.

UE Side Operation

For any of the embodiments described herein, a UE may combineduplications of a TB received over different carriers. For repetition,log likelihood ratios (LLRs) of transmissions received over differentcarriers can be added before feeding to the decoder. In this case, HARQfeedback may be generated once. Combining duplications may involve theHARQ entities of the group of carriers sharing soft buffers of the HARQentities. In another embodiment, selection combining is performed.Alternatively, the UE does not combine duplications of a TB receivedover different carriers, and sends ACK/NACK for each transmission.

An example UE side implementation is depicted in FIG. 10 . Shown are twoLLRs produced for TBs received on the SCC 1000 and PCC 1002respectively. These can be combined at 1004 before being passed to thedecoder 1006. Alternatively, the LLRs are passed separately to thedecoder 1006 where they are decoded separately.

HARQ Codebook

HARQ feedback generated for carrier aggregation with the same HARQprocess shared across multiple carriers may require a modified HARQcodebook generation. A UE may generate a common HARQ feedback aftercombining the duplications across the carriers. In some embodiments, aHARQ codebook is defined which specifies HARQ feedback for one or moreof the embodiments described herein. The size of HARQ codebook can bedecided by:

Downlink assignment index (DAI) (e.g. 2 bit), informing the UE about thenumber of downlink transmissions for which a single hybrid-ARQacknowledgment should be generated. The codebook collects a combinationof ACK/NACK feedbacks, where the number of ACK/NACKs combined can bedynamically indicated in the DCI in the form of DAI;

HARQ codebook contains ACK/NACK of one or more transmissions, some canbe codeblock group (CBG)-based, some can be transport block (TB)-based.

FIG. 11 shows an example, where a UE may have different types of traffictransmission ongoing, such as enhanced mobile broadband (eMBB) and ultrareliable low latency communications (URLLC). eMBB transmission can becode block group (CBG)-based and URLLC transmission can be TB-based. Inthis example, each eMBB transmission is configured with up to two CBGsfor feedback. DAI (N, i) indicates ith feedback in the codebook wherethere are N total feedbacks combined in the message. For example, DAI(3,1) and DAI (3,2), each have two sub-fields within the ACK/NACKmessage for corresponding downlink transmission, each sub-fieldaccounting for a CBG. DAI (3,3) is common for CC3 and CC4 because the UEis configured to have a common HARQ feedback for the same TBtransmission over CC3 and CC4. Mapping of the DAIs to the fields may bearranged in the order of the CC index.

Referring now to FIG. 12 , shown is a block diagram of a system fortransmission over unlicensed spectrum, using auxiliary HARQ Processesfor multi-carrier operations, in accordance with an embodiment of theinvention. Auxiliary HARQ processes may also be referred to as switchedHARQ processes. Auxiliary and switched HARQ processes may be usedinterchangeably.

On the transmit side, there is a transmit RLC 1100, transmit MAC 1102(including MAC scheduler) that implements a respective HARQ entity1104,1106,1108 for each of three component carriers 1110,1112,1114. Atthe receiver side, there is a receive MAC 1128 that implements arespective HARQ entity 1120,1122,1124 for each of the three componentcarriers 1110,1112,1114, and a receive RLC 1126.

In operation, initial transmissions are made using one componentcarriers, and using the associated HARQ entity, with a HARQ process ID.If no positive acknowledgement (ACK) has been received from the receiverwithin an expected window of time after the transmission, aretransmission is initiated using the same component carrier and HARQprocess ID.

Because LBT is used before transmissions, a retransmission may or maynot be transmitted depending on the availability of the channel. Atransmission that is not transmitted is said to be blocked. Thetransmitter MAC 1102 monitors (for example using a timer) the blockingtime during which a retransmission of a HARQ process (HARQ ID i) thatwas initiated on a component carrier (CCx) is being blocked. As analternative to using a timer, a count of the number of retransmissionattempts can be made, with a certain number of retransmission attemptsfunctioning as a trigger for activating an auxiliary HARQ process, asdetailed below.

In a specific example, a timer at the transmitter MAC 1102 is started atthe instant at which the HARQ feedback of process i is due on CCx. Inthis case, the timer also accounts for the pre-defined window of timewithin which the HARQ feedback is expected. In another embodiment, thetimer can be started once the corresponding negative acknowledgement(NACK) has been received or the corresponding HARQ feedback is overdue.In the case of the HARQ feedback being overdue, the timer accounts aswell for the blocking delay of the feedback at the receiving end.

The timer at the transmitter MAC 1102 is specific to the UE's HARQprocess i on CCx if the transmitter resets once the retransmissionattempt is successful or after the timer expires (or reaches ahigher-layer configured maximum). Alternatively, the timer can bespecific to the HARQ entity such that the timer's value can beaccumulated from the associated set of HARQ processes until the timerexpires (or reaches a greater higher-layer configured maximum), and thena set of auxiliary HARQ processes are activated concurrently as a groupevent.

Upon expiry of the timer, the transmitter MAC activates an auxiliaryHARQ process on a different component carrier CCy and schedules and thentransmits a retransmission using the auxiliary HARQ process. In someembodiments, for a given CCx, another component carrier CCy forauxiliary retransmission is chosen in advance. In other embodiments, CCyis dynamically selected from a carrier or cell group that the receiverhas been configured to use.

The receiver MAC 1128 can also monitor the excess retransmission delaytime beyond a HARQ round trip time (RTT) timer value that has beenpre-configured through higher-layer signaling such as RRC.

The RTT timer at the receiver MAC 1128 can be initialized at the instantat which the HARQ RTT timer elapses from the last (re)transmission ofHARQ process i on CCx. The timer can be reset upon receiving theretransmission of HARQ process i.

Similar to the transmitter side timer, the timer at the receiver MAC iseither specific to the UE's HARQ process i on CCx or the HARQ entity onCCx.

Once the timer value in the receiver exceeds a pre-configured parameter(e.g. HARQReTxMaxDelay), the receiver MAC 1128 can trigger the receiveHARQ to change to the auxiliary HARQ process and indicate the change tothe transmitter, for example through control signaling over a morereliable (e.g., licensed) CC.

Referring again to FIG. 12 , in a specific example, a TB transmission istaking place using HARQ ID 3 on CC1 1112. A retransmission is attempted,using the same HARQ ID and component carrier. After the retransmissionis blocked for the duration of a timer (Dmax), the Transmit MAC 1102activates a transmit auxiliary HARQ process on a different componentcarrier. In the example illustrated, the auxiliary HARQ process isinitiated with HARQ ID 8 on CC2 1114. The auxiliary HARQ process isscheduled and activated on CC2. Correspondingly, in the receiveractivates a receive auxiliary HARQ process to receive the retransmissionon CC2.

In a specific example, retransmissions of the TB associated with theactive HARQ process (HARQ ID i) on CCx can be changed by the transmitterto the first idle HARQ process j on a component carrier. Note thatdifferent component carriers may be associated with the same ordifferent cells/transmission/receiving point (TRP).

In some embodiments, to reduce the overhead associated with indicatingthe HARQ process ID to be activated on CCy, a subset of such ‘auxiliary’HARQ process IDs can be defined using a semi-statically configuredmapping table or rule. If the first auxiliary HARQ process ID in thesubset is busy, then the second auxiliary HARQ process ID in the subsetis selected, and can be indicated to the receiver using fewer bits thanwould be required to select from an entire set of HARQ process IDs.Alternatively, the auxiliary HARQ process ID is pre-configured for agiven HARQ process on CCx. For grant-free transmissions, such asgrant-free uplink transmissions, this can be a one-to-many mapping, withthe transmitter responsible for selecting an available one of the mappedHARQ processes. For scheduled uplink and downlink transmissions, thiscan be a one-to-many mapping, with the scheduler responsible forselecting an available one of the mapped HARQ processes. Alternatively,the auxiliary HARQ process ID (optionally along with the carrier indexof CCy) may be signaled in a DCI.

In some embodiments, there is a default mode of operation that is usedif no auxiliary HARQ process is available, in whichretransmissions/repetitions are performed using the same componentcarrier as an original transmission.

Once the receiver detects the change in the component carrier used forretransmissions, the corresponding idle auxiliary HARQ process isactivated on CCy along with its receive FEC buffer.

Referring to FIG. 13 , shown is another view of the system of FIG. 11 ,showing additional steps that may be implemented following successful TBdecoding in the receiver. The receive side RLC 1126 collects asuccessfully decoded TB at 1210 (from either process i or its activatedauxiliary process(es)) and updates its receive window.

An indication 1200 to free up the main and associated auxiliaryprocess(es) and clear their FEC buffers is provided to respective HARQentities directly or through the MAC or through the receiver RLCsub-layer. A decode success indication (e.g. ACK) 1202 is transmittedback to the receiver. In some embodiments this can be sent on any of thecomponent carriers involved.

Upon receiving a decode success indication, the transmit side RLC 1100updates its PDU transmit window, and generates an indication 1204 tofree up all associated processes and clear their circular transmitbuffers, which is provided to respective HARQ entities. Alternatively,the HARQ entity for which a success indication has been received cansignal the remaining HARQ entities through the transmit MAC to cleartheir respective transmit buffers.

In some embodiments, one or more of the methods described herein appliedto New Radio-unlicensed (NR-U) uplink grant based retransmissions inrespect of initial uplink grant based transmissions, where the uplinkgrant of retransmission and granted uplink resource can be in differentcomponent carrier from the initial transmission.

In some embodiments, the UE is configured to inform the network (forexample by informing a gNB) of its capability to soft-combine TBsreceived across multiple CCs. Based on this information, the network canthen decide on the redundancy version to use with auxiliary HARQretransmission. For example, for transmission to a UE that is notcapable of such soft-combining, the retransmission can be a completeretransmission of the original TB. For example, for transmission to a UEthat is not capable of such soft-combining, the retransmission can be acomplete independent retransmission of the original TB.

In some embodiments, the network transmits a configuration of auxiliaryHARQ Processes/Mapping Rule. For example, a gNB may semi-staticallyconfigure the UEs with the auxiliary HARQ processes through higher layersignaling, e.g., RRC. The mapping rule can be signaled as a lookup tableor parameters of a pre-determined formulae/arithmetic procedure.

In some embodiments, the mapping rule is a lookup table. An example isshown in FIG. 14A which maps a main HARQ ID i to the pre-configuredauxiliary HARQ Process IDs j. The example shown in FIG. 14A also showsthe mapping of main HARQ ID i to the pre-configured auxiliary HARQProcess IDs k and l. As used herein, a main HARQ ID and an original HARQID are interchangeable.

In some embodiments, wherein a pre-determined formula/arithmeticprocedure is employed, an index offset and/or a cyclic shift is used tocalculate the auxiliary HARQ Process ID. The cyclic shift register canhold the HARQ ID i in n binary bits concatenated with a predefinednumber of bits that are started with zeros or the carrier indicationfield (CIF) bits of CCx. The index offset is applied to the cyclic shiftregister to avoid corner cases such as all zeros or all ones HARQ ID i.An all zeros or all ones HARQ ID i is a situation where a valuerepresenting HARD ID i is represented in the shift register as allbinary zeros or all binary ones. An example is shown in FIG. 14B. Insome embodiments, a one-to-many mapping rule involves applying a numberof binary ID shifts, each binary ID shift having an associated indexthat can be used to communicate a specific binary ID shift in dynamicsignaling. In some embodiments, both the index offset, and the number ofbinary ID shifts are used in combination.

In some embodiments one or more parameters are signaled, which areapplied to a formula. An example is shown in FIG. 14C. In FIG. 14C, theresource identifier CIF of CCx is used in concatenation with the n bitsof the HARQ ID of the HARQ Process i. Other techniques may be used tocombine the resource identifier CIF and the HARQ ID, such as addition,subtraction, multiplication, and so on.

Dynamic Indication of Switching to Auxiliary HARQ

If the network needs to retransmit HARQ process i on CCx but its LBTbefore the retransmission fails on CCx or a BWP thereof, after receivinga NACK or not receiving any feedback for a preset duration, a DCI forthe retransmission takes place on CCy or a BWP thereof instead of CCxusing one of the following methods depending on whether a mapping ruleor formula is pre-configured and whether the DCI is cross-carrierscheduling or self-scheduling.

Explicit Indication in DCI (No Mapping Rule is Pre-Configured)

-   -   a. Cross-carrier scheduling DCI (e.g., from a licensed PCC):        -   The DCI comprises indications of one or more of:        -   identifier of the original component carrier CCx;        -   original HARQ process ID i on CCx;        -   identifier of the new component carrier CCy on which the            auxiliary HARQ process is activated;        -   auxiliary HARQ process ID;        -   the same TB as switched original;        -   a new resource allocation corresponding to CCy (optionally,            resource allocation is in units of resource blocks (RBs),            and a resource block allocation for CCy include a number of            resource blocks that is the same as a number of RBs            allocated on CCx);        -   either same or a different modulation and coding scheme            (MCS) based on the new RB allocation;        -   redundancy version (optionally based on UE capability of            soft-combining across component carriers);        -   Same new data indicator (NDI) as original (non-toggled).    -   b. Self-carrier scheduling DCI (transmitted on intended CC):        -   The DCI comprises indications of one or more of:        -   Index of original carrier CCx. However, this is not needed            if a pool of HARQ processes is shared across the CCs);        -   original HARQ process i on CCx;        -   auxiliary HARQ process ID;        -   the same TB as switched original;        -   a new resource block allocation corresponding to CCy            (optionally, same number of RBs can be maintained);        -   either same or a different modulation and coding scheme            (MCS) based on the new RB Allocation;        -   redundancy version (optionally based on UE capability of            soft-combining across component carriers);        -   Same new data indicator (NDI) as original (non-toggled).

Implicit Indication in DCI (Mapping Rule is Pre-Configured)

-   -   a. Cross-carrier scheduling DCI (e.g., from licensed PCC):    -   Format A1: The DCI comprises indications of one or more of:        -   original HARQ process i on CCx;        -   identifier of the new component carrier CCy on which the            auxiliary HARQ process is activated;        -   Shift Index (Number of cyclic shifts for the mapping rule or            number of table entries to skip in a mapping table);        -   Format Bit (for UE to distinguish between formats A1 and A2            if they are identical in size);        -   the same TB as switched original;        -   a new resource block allocation corresponding to CCy            (optionally, same number of RBs can be maintained);        -   either same or a different modulation and coding scheme            (MCS) based on the new RB Allocation;        -   redundancy version (optionally based on UE capability of            soft-combining across component carriers);        -   same new data indicator (NDI) as original (non-toggled).

Using the indicated CCy and switched HARQ ID i, the UE can to obtain thepair (CCx, Aux-HARQ ID j). As a validation of the received DCI, UE cancheck if obtained CCx had the HARQ ID i among its associated processes.This is in addition to the same TB size as original and the non-toggledNDI field w.r.t that of the original DCI scheduled process i.

-   -   Format A2: The DCI comprises indications of one or more of:        -   Auxiliary HARQ process ID j;        -   Identifier of original component carrier CCx;        -   Shift Index (Number of cyclic shifts for the mapping rule or            number of table entries to skip in a mapping table);        -   Format Bit (for UE to distinguish between formats A1 and A2            if they are identical in size);        -   the same TB as switched original;        -   a new resource block allocation corresponding to CCy            (optionally, same number of RBs can be maintained);        -   either same or a different modulation and coding scheme            (MCS) based on the new RB Allocation;        -   redundancy version (optionally based on UE capability of            soft-combining across component carriers);        -   same new data indicator (NDI) as original (non-toggled).

Using the indicated CCx, which is not the CC ID being scheduled unlikelegacy cross-carrier scheduling DCI formats, and the auxiliary HARQ IDj, the UE can to obtain the pair (CCy, HARQ ID i). As a validation ofthe received DCI, UE can check if obtained HARQ ID i is among theassociated processes of CCx. This is in addition to the same TB size asoriginal and the non-toggled NDI field w.r.t that of the original DCIscheduled process i.

-   -   b. Self-carrier scheduling DCI:    -   Format B1: The DCI comprises indications of one or more of:        -   original HARQ process i on CCx;        -   Shift Index (Number of cyclic shifts for the mapping rule or            number of table entries to skip in a mapping table            corresponding to scheduled CCy);        -   Format Bit (for UE to distinguish between formats B1 and B2            if they are identical in size);        -   the same TB as switched original;        -   a new resource block allocation corresponding to CCy            (optionally, same number of RBs can be maintained);        -   either same or a different modulation and coding scheme            (MCS) based on the new RB Allocation;        -   redundancy version (optionally based on UE capability of            soft-combining across component carriers);        -   Same new data indicator (NDI) as original (non-toggled).

Using the self-carrier index of CCy and switched HARQ ID i, the UE canto obtain the pair (CCx, Aux-HARQ ID j). In some embodiments, Format B1can imply that j=i for simplicity As a validation of the received DCI,UE can check if obtained CCx had the HARQ ID i among its associatedprocesses. This is in addition to the same TB size as original and thenon-toggled NDI filed w.r.t that of the original DCI scheduled processi.

-   -   Format B2: The DCI comprises indications of one or more of:        -   Auxiliary HARQ process ID j;        -   Shift Index (Number of cyclic shifts for the mapping rule or            number of table entries to skip in a mapping table            corresponding to scheduled CCy);        -   Format Bit (for UE to distinguish between formats A1 and A2            if they are identical in size);        -   the same TB as switched original;        -   a new resource block allocation corresponding to CCy            (optionally, same number of RBs can be maintained);        -   either same or a different modulation and coding scheme            (MCS) based on the new RB Allocation;        -   redundancy version (optionally based on UE capability of            soft-combining across component carriers);        -   same new data indicator (NDI) as original (non-toggled).

Using the scheduled CCy and the auxiliary HARQ ID j, the UE can toobtain the pair (CCx, HARQ ID i). In some embodiments, Format B2 canimply that i=j for simplicity. As a validation of the received DCI, UEcan check if obtained HARQ ID i is among the associated processes ofCCx. This is in addition to the same TB size as original and thenon-toggled NDI filed w.r.t that of the original DCI scheduled processi.

In some embodiments, downlink assignments for subsequent retransmissionsof the same TB on CCy follow normal procedure indicating the auxiliaryHARQ ID.

FIG. 15A illustrates a flow diagram of example operations occurring inan access node operating in accordance with the example embodimentspresented herein.

Operations begin with the access node sending an assignment of atransmission with HARQ Process ID i (block 1505). The transmission maybe of a transmission block in a first network resource. Examples ofnetwork resources include time resources, frequency resources,time-frequency resources, code resources, carriers, component carriers,cells, or BWPs. The access node sends an assignment of a transmissionwith HARQ Process ID j (block 1507). The transmission may be of atransmission block in a second network resource. The access node detectsan indication that the HARQ Process ID i and the HARQ Process ID j mapto the same transmission block (block 1509). As an example, the accessnode detects that the indication indicates independent scheduling ordata duplication in different HARQ Process IDs. As another example, theaccess node detects expiration of a RTT timer (either a transmit RTTtimer for situations when the access node is transmitting or a receiveRTT timer for situations when the access node is receiving) as theindication. The access node communicates the transmission associatedwith either of the HARQ Process IDs (block 1511). As used in thisdisclosure, communication applies to transmitting the transmission,receiving the transmission, or both transmitting and receiving thetransmission.

FIG. 15B illustrates a flow diagram of example operations occurring in aUE operating in accordance with the example embodiments presentedherein.

Operations begin with the UE receiving an assignment of a transmissionwith HARQ Process ID i (block 1555). The transmission may be of atransmission block in a first network resource. The UE receives anassignment of a transmission with HARQ Process ID j (block 1557). Thetransmission may be of a transmission block in a second networkresource. The UE detects an indication that the HARQ Process ID i andthe HARQ Process ID j map to the same transmission block (block 1559).As an example, the UE detects that the indication indicates independentscheduling or data duplication in different HARQ Process IDs. As anotherexample, the UE detects expiration of a RTT timer (either a transmit RTTtimer for situations when the UE is transmitting or a receive RTT timerfor situations when the UE is receiving) as the indication. The UEcommunicates the transmission associated with either of the HARQ ProcessIDs (block 1561).

FIG. 16A illustrates a flow diagram of example operations occurring inan access node transmitting when a network resource becomes blocked.

Operations begin with the access node sending an assignment of atransmission with HARQ Process ID i (block 1605). The transmission maybe of a transmission block in a first network resource. The access nodesends an assignment of a transmission with HARQ Process ID j (block1607). The transmission may be of a transmission block in a secondnetwork resource. The access node transmits the transmission on networkresource X that is associated with HARQ Process ID i (block 1609). Theaccess node performs a check to determine if feedback associated withHARQ Process ID i is blocked (block 1611). As an example, the feedbackassociated with HARQ Process ID i is blocked if the access node does notreceive the feedback before expiration of a transmit RTT associated withthe HARQ Process ID i. If the feedback is not blocked, the access nodereturns to continue checking.

If the feedback is blocked, the access node determines the HARQ ProcessID j (block 1613). As an example, the access node determines the HARQProcess ID j utilizing a lookup table, such as shown in FIG. 14A. Asanother example, the access node determines the HARQ Process ID j usinga pre-determined formula/arithmetic procedure with or withoutparameters, such as shown in FIGS. 14B and 14C. The access nodetransmits on resource Y that is associated with HARQ Process ID j (block1615).

FIG. 16B illustrates a flow diagram of example operations occurring in aUE receiving when a network resource becomes blocked.

Operations begin with the UE receiving an assignment of a transmissionwith HARQ Process ID i (block 1655). The transmission may be of atransmission block in a first network resource. The UE receives anassignment of a transmission with HARQ Process ID j (block 1657). Thetransmission may be of a transmission block in a second networkresource. The UE receives the transmission on resource X that isassociated with HARQ Process ID i (block 1669). The UE performs a checkto determine if a retransmission is needed (block 1671). As an example,if the UE is unable to successfully decode the transmission, aretransmission is needed. If a retransmission is not needed, operationscomplete.

If a retransmission is needed, the UE transmits a NACK and performs acheck to determine if resource X is blocked (block 1673). As an example,the resource X is blocked if a retransmission of the transmission is notreceived before expiration of a receive RTT associated with the HARQProcess ID i. If the resource X is not blocked, the UE returns tocontinue checking. If the resource X is blocked, the UE determines theHARQ Process ID j (block 1675). As an example, the UE determines theHARQ Process ID j utilizing a lookup table, such as shown in FIG. 14A.As another example, the UE determines the HARQ Process ID j using apre-determined formula/arithmetic procedure with or without parameters,such as shown in FIGS. 14B and 14C. The UE receives on resource Y thatis associated with HARQ Process ID j (block 1675).

The following provides a non-limiting list of example embodiments of thepresent disclosure:

Example embodiment 1. A computer-implemented method comprising sending,by an access node, a first assignment for a first transmission with afirst HARQ process identifier (process ID) in a first network resource,sending, by the access node, a second assignment for a secondtransmission with a second HARQ process ID in a second network resource,wherein the first network resource and the second network resourcediffer in a domain other than a time domain, detecting, by the accessnode, an indication indicating that the first HARQ process ID and thesecond HARQ process ID map to a same TB, and communicating, by theaccess node, with a UE, a transmission associated with at least one ofthe first HARQ process ID or the second HARQ process ID.

Example embodiment 2. The computer-implemented method of exampleembodiment 1, wherein communicating the transmission comprisestransmitting, by the access node, the transmission to the UE.

Example embodiment 3. The computer-implemented method of exampleembodiment 1, wherein communicating the transmission comprisesreceiving, by the access node, the transmission from the UE.

Example embodiment 4. The computer-implemented method of exampleembodiment 1, wherein the indication is a semi-static configuration.

Example embodiment 5. The computer-implemented method of exampleembodiment 1, wherein the indication is a combination of a semi-staticconfiguration and dynamic signaling.

Example embodiment 6. The computer-implemented method of exampleembodiment 1, wherein the indication comprises an indication indicatingthat a pool of HARQ process IDs are common across at least the first andsecond network resources, wherein the first HARQ process ID and thesecond HARQ process ID are the same to indicate that the first andsecond HARQ process IDs map to the TB.

Example embodiment 7. The computer-implemented method of exampleembodiment 1, wherein the indication comprises an indication indicatingthat a subset of a pool of HARQ process IDs are common across at leastthe first and second network resources, wherein the first HARQ processID and the second HARQ process ID are the same and belong to the subsetto indicate that the first and second HARQ process IDs map to the TB.

Example embodiment 8. The computer-implemented method of exampleembodiment 1.38, wherein the indication comprises an indicationindicating that a subset of a pool of HARQ process IDs are common acrossa subset of a set of network resources, wherein the first and secondHARQ process IDs are the same and belong to the subset of the pool andthe first and second network resources belong to the subset of the setof network resources to indicate that the first and second HARQ processIDs map to the TB.

Example embodiment 9. The computer-implemented method of exampleembodiment 1, wherein the indication comprises a field in the secondassignment indicating that the second assignment is in respect of aretransmission of the TB.

Example embodiment 10. The computer-implemented method of exampleembodiment 9, wherein the indication comprises a semi-staticconfiguration that associates the second HARQ process ID with the firstHARQ process ID, such that the first assignment including the first HARQprocess ID, the second assignment including the second HARQ process ID,and the field in the second assignment together indicate that the firstand second HARQ process IDs map to the TB.

Example embodiment 11. The computer-implemented method of exampleembodiment 9, wherein for the first assignment and the second assignmentto be in respect of the same TB, the first assignment and the secondassignment are sent within a specified time window of one another.

Example embodiment 12. The computer-implemented method of exampleembodiment 11, wherein the specified time window is specified in termsof a number of time slots, mini-slots, subframes, or symbols.

Example embodiment 13. The computer-implemented method of exampleembodiment 1, wherein the indication comprises a first field in thefirst assignment indicating that there will be an assignment in respectto the TB on a different network resource, and a second field in thesecond assignment indicating that the second assignment is in respect tothe TB transported on the different network resource.

Example embodiment 14. The computer-implemented method of exampleembodiment 13, wherein the indication further comprises at least onesemi-statically configured mapping rule that associates the first HARQprocess ID on the first network resource with the second HARQ process IDon the second network resource, and wherein the first assignmentincluding the first field and the second assignment including the secondfield together indicate that the first and second assignments are inrespect to the TB only when the first HARQ process ID is associated withthe second HARQ process ID through the at least one mapping rule.

Example embodiment 15. The computer-implemented method of exampleembodiment 1, wherein communicating a transmission associated with atleast one of the first HARQ process ID or the second HARQ process IDcomprises communicating a first transmission associated with the firstHARQ process ID on the first network resource and communicating a secondtransmission associated with the second HARQ process ID on the secondnetwork resource.

Example embodiment 16. The computer-implemented method of exampleembodiment 15, further comprising processing, by the access node, thefirst transmission to produce a first set of LLRs, processing, by theaccess node, the second transmission to produce a second set of LLRs,combining, by the access node, the first set of LLRs and the second setof LLRs to produce a combined set of LLRs, and decoding, by the accessnode, the TB transmitted in the first transmission and the secondtransmission in accordance with the combined set of LLRs.

Example embodiment 17. The computer-implemented method of exampleembodiment 1, further comprising sending a HARQ codebook configurationindicating ACK/NACK resources used for transmitting a first ACK/NACK inrespect to the TB or versions of the TB received over multiple networkresources.

Example embodiment 18. The computer-implemented method of exampleembodiment 16, wherein the HARQ codebook configuration indicates anACK/NACK resource for transmitting a second ACK/NACK in respect to theTB or versions of the TB received over multiple network resources.

Example embodiment 19. The computer-implemented method of exampleembodiment 1, further comprising transmitting, by the access node, athird ACK/NACK only on the first network resource.

Example embodiment 20. The computer-implemented method of exampleembodiment 1, further comprising transmitting, by the access node, afourth ACK/NACK on the first network resource and the second networkresource.

Example embodiment 21. The computer-implemented method of exampleembodiment 1, wherein the first network resource is an unlicensednetwork resource.

Example embodiment 22. The computer-implemented method of exampleembodiment 21, wherein the indication comprises at least one parameterupon which the access node determines whether a switch from the firstHARQ process ID on the first network resource to the second HARQ processID on the second network resource has occurred.

Example embodiment 23. The computer-implemented method of exampleembodiment 21, wherein the first assignment comprises a first TB sizeindicator indicating a size of the first TB and a first NDI, wherein thesecond assignment comprises a second indicator indicating the size ofthe second TB a second NDI, wherein the first assignment and the secondassignment indicate the same TB size, and wherein the first NDI and thesecond NDI are the same.

Example embodiment 24. The computer-implemented method of exampleembodiment 21, wherein the second assignment comprises an indicatorindicating at least one of an identifier of the first network resourceor the first HARQ process ID.

Example embodiment 25. The computer-implemented method of exampleembodiment 22, wherein the at least one parameter comprises a timeoutvalue of a timer initialized by the access node after a HARQ RTT timerelapses from a last transmission in respect to the TB on the firstnetwork resource, such that the timer elapsing indicates a subsequenttransmission in respect to the TB will occur on a different networkresource.

Example embodiment 26. The computer-implemented method of exampleembodiment 25, wherein the RTT timer elapsing further indicates to theaccess node to send the second assignment for the transmission of the TBwith the second HARQ process ID in the second network resource.

Example embodiment 27. The computer-implemented method of exampleembodiment 21, wherein the indication further comprises asemi-statically configured association between the first HARQ process IDand the second HARQ process ID.

Example embodiment 28. The computer-implemented method of exampleembodiment 21, wherein the indication further comprises at least onemapping, rule, or parameter in respect to a rule that associates thesecond HARQ process ID with the first HARQ process ID.

Example embodiment 29. The computer-implemented method of exampleembodiment 27, wherein the indication comprises an index offsetindicating a binary index offset between the first and second HARQprocess IDs.

Example embodiment 30. The computer-implemented method of exampleembodiment 27, wherein the indication comprises a number of binaryshifts between the first and second HARQ process IDs.

Example embodiment 31. The computer-implemented method of exampleembodiment 27, wherein the indication comprises an index indicating abinary offset and a number of binary shifts that together associate thesecond HARQ process ID with the first HARQ process ID.

Example embodiment 32. The computer-implemented method of exampleembodiment 27, wherein the indication comprises an index indicating anumber of binary shifts, and wherein a binary offset and the number ofbinary shifts together associate the second HARQ process ID with thefirst HARQ process ID.

Example embodiment 33. The computer-implemented method of exampleembodiment 27, wherein the indication comprises an index indicating abinary offset and a number of binary shifts that together with asemi-statically configured rule or formula associate the second HARQprocess ID with the first HARQ process ID.

Example embodiment 34. A computer-implemented method comprising sending,by an access node, a first assignment for a first transmission with afirst HARQ process identifier (process ID) in a first network resource,sending, by the access node, a second assignment for a secondtransmission with a second HARQ process ID in a second network resource,wherein the first HARQ process ID differs from the second HARQ processID, detecting, by the access node, an indication indicating that thefirst HARQ process ID and the second HARQ process ID map to a same TB,and communicating, by the access node, with a UE, a transmissionassociated with at least one of the first HARQ process ID or the secondHARQ process ID.

Example embodiment 35. An access node comprising a non-transitory memorystorage comprising instructions, and one or more processors incommunication with the memory storage, wherein the one or moreprocessors execute the instruction to send a first assignment for afirst transmission with a first HARQ process identifier (process ID) ina first network resource, send a second assignment for a secondtransmission with a second HARQ process ID in a second network resource,wherein the first network resource and the second network resourcediffer in a domain other than a time domain, detect an indicationindicating that the first HARQ process ID and the second HARQ process IDmap to a same TB, and communicate with a UE, a transmission associatedwith at least one of the first HARQ process ID or the second HARQprocess ID.

Example embodiment 36. An access node comprising a non-transitory memorystorage comprising instructions, and one or more processors incommunication with the memory storage, wherein the one or moreprocessors execute the instruction to sending a first assignment for afirst transmission with a first HARQ process identifier (process ID) ina first network resource, send a second assignment for a secondtransmission with a second HARQ process ID in a second network resource,wherein the first HARQ process ID differs from the second HARQ processID, detect an indication indicating that the first HARQ process ID andthe second HARQ process ID map to a same TB, and communicate, with a UE,a transmission associated with at least one of the first HARQ process IDor the second HARQ process ID.

Example embodiment 37. A computer-implemented method comprisingreceiving, by a UE, a first assignment for a first transmission with afirst HARQ process identifier (process ID) in a first network resource,receiving, by the UE, a second assignment for a second transmission witha second HARQ process ID in a second network resource, wherein the firstnetwork resource and the second network resource differ in a domainother than a time domain, detecting, by the UE, an indication indicatingthat the first HARQ process ID and the second HARQ process ID map to asame TB, and communicating, by the UE, with an access node, atransmission associated with at least one of the first HARQ process IDor the second HARQ process ID.

Example embodiment 38. The computer-implemented method of exampleembodiment 37, wherein the indication comprises an indication indicatingthat a subset of a pool of HARQ process IDs are common across at leastthe first and second network resources, wherein the first HARQ processID and the second HARQ process ID are the same and belong to the subsetto indicate that the first and second HARQ process IDs map to the TB.

Example embodiment 39. The computer-implemented method of exampleembodiment 37, wherein the indication comprises an indication indicatingthat a subset of a pool of HARQ process IDs are common across a subsetof a set of network resources, wherein the first and second HARQ processIDs are the same and belong to the subset of the pool and the first andsecond network resources belong to the subset of the set of networkresources to indicate that the first and second HARQ process IDs map tothe TB.

Example embodiment 40. The computer-implemented method of exampleembodiment 37, wherein the indication comprises a field in the secondassignment indicating that the second assignment is in respect of aretransmission of the TB.

Example embodiment 41. The computer-implemented method of exampleembodiment 40, wherein for the first assignment and the secondassignment to be in respect of the same TB, the first assignment and thesecond assignment are received within a specified time window of oneanother.

Example embodiment 42. The computer-implemented method of exampleembodiment 41, wherein the specified time window is specified in termsof a number of time slots, mini-slots, subframes, or symbols.

Example embodiment 43. The computer-implemented method of exampleembodiment 37, wherein communicating a transmission associated with atleast one of the first HARQ process ID or the second HARQ process IDcomprises receiving a first transmission associated with the first HARQprocess ID on the first network resource and receiving a secondtransmission associated with the second HARQ process ID on the secondnetwork resource.

Example embodiment 44. The computer-implemented method of exampleembodiment 43, further comprising processing, by the UE, the firsttransmission to produce a first set of LLRs, processing, by the UE, thesecond transmission to produce a second set of LLRs, combining, by theUE, the first set of LLRs and the second set of LLRs to produce acombined set of LLRs, and decoding, by the UE, the TB transmitted in thefirst transmission and the second transmission in accordance with thecombined set of LLRs.

Example embodiment 45. The computer-implemented method of exampleembodiment 37, further comprising transmitting, by the UE, ACK/NACKfeedback only on the first network resource.

Example embodiment 46. The computer-implemented method of exampleembodiment 45, further comprising receiving a HARQ codebookconfiguration indicating ACK/NACK resources used for transmitting anACK/NACK in respect to the TB or versions of the TB received overmultiple network resources.

FIG. 17 illustrates an example communication system 1700. In general,the system 1700 enables multiple wireless or wired users to transmit andreceive data and other content. The system 1700 may implement one ormore channel access methods, such as code division multiple access(CDMA), time division multiple access (TDMA), frequency divisionmultiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA(SC-FDMA), or non-orthogonal multiple access (NOMA).

In this example, the communication system 1700 includes electronicdevices (ED) 1710 a-1710 c, radio access networks (RANs) 1720 a-1720 b,a core network 1730, a public switched telephone network (PSTN) 1740,the Internet 1750, and other networks 1760. While certain numbers ofthese components or elements are shown in FIG. 17 , any number of thesecomponents or elements may be included in the system 1700.

The EDs 1710 a-1710 c are configured to operate or communicate in thesystem 1700. For example, the EDs 1710 a-1710 c are configured totransmit or receive via wireless or wired communication channels. EachED 1710 a-1710 c represents any suitable end user device and may includesuch devices (or may be referred to) as a user equipment or device (UE),wireless transmit or receive unit (WTRU), mobile station, fixed ormobile subscriber unit, cellular telephone, personal digital assistant(PDA), smartphone, laptop, computer, touchpad, wireless sensor, orconsumer electronics device.

The RANs 1720 a-1720 b here include base stations 1770 a-1770 b,respectively. Each base station 1770 a-1770 b is configured towirelessly interface with one or more of the EDs 1710 a-1710 c to enableaccess to the core network 1730, the PSTN 1740, the Internet 1750, orthe other networks 1760. For example, the base stations 1770 a-1770 bmay include (or be) one or more of several well-known devices, such as abase transceiver station (BTS), a Node-B (NodeB), an evolved NodeB(eNodeB), a Next Generation (NG) NodeB (gNB), a Home NodeB, a HomeeNodeB, a site controller, an access point (AP), or a wireless router.The EDs 1710 a-1710 c are configured to interface and communicate withthe Internet 1750 and may access the core network 1730, the PSTN 1740,or the other networks 1760.

In the embodiment shown in FIG. 17 , the base station 1770 a forms partof the RAN 1720 a, which may include other base stations, elements, ordevices. Also, the base station 1770 b forms part of the RAN 1720 b,which may include other base stations, elements, or devices. Each basestation 1770 a-1770 b operates to transmit or receive wireless signalswithin a particular geographic region or area, sometimes referred to asa “cell.” In some embodiments, multiple-input multiple-output (MIMO)technology may be employed having multiple transceivers for each cell.

The base stations 1770 a-1770 b communicate with one or more of the EDs1710 a-1710 c over one or more air interfaces 1790 using wirelesscommunication links. The air interfaces 1790 may utilize any suitableradio access technology.

It is contemplated that the system 1700 may use multiple channel accessfunctionality, including such schemes as described above. In particularembodiments, the base stations and EDs implement 5G New Radio (NR), LTE,LTE-A, or LTE-B. Of course, other multiple access schemes and wirelessprotocols may be utilized.

The RANs 1720 a-1720 b are in communication with the core network 1730to provide the EDs 1710 a-1710 c with voice, data, application, Voiceover Internet Protocol (VoIP), or other services. Understandably, theRANs 1720 a-1720 b or the core network 1730 may be in direct or indirectcommunication with one or more other RANs (not shown). The core network1730 may also serve as a gateway access for other networks (such as thePSTN 1740, the Internet 1750, and the other networks 1760). In addition,some or all of the EDs 1710 a-1710 c may include functionality forcommunicating with different wireless networks over different wirelesslinks using different wireless technologies or protocols. Instead ofwireless communication (or in addition thereto), the EDs may communicatevia wired communication channels to a service provider or switch (notshown), and to the Internet 1750.

Although FIG. 17 illustrates one example of a communication system,various changes may be made to FIG. 17 . For example, the communicationsystem 1700 could include any number of EDs, base stations, networks, orother components in any suitable configuration.

FIGS. 18A and 18B illustrate example devices that may implement themethods and teachings according to this disclosure. In particular, FIG.18A illustrates an example ED 1810, and FIG. 18B illustrates an examplebase station 1870. These components could be used in the system 1700 orin any other suitable system.

As shown in FIG. 18A, the ED 1810 includes at least one processing unit1800. The processing unit 1800 implements various processing operationsof the ED 1810. For example, the processing unit 1800 could performsignal coding, data processing, power control, input/output processing,or any other functionality enabling the ED 1810 to operate in the system1700. The processing unit 1800 also supports the methods and teachingsdescribed in more detail above. Each processing unit 1800 includes anysuitable processing or computing device configured to perform one ormore operations. Each processing unit 1800 could, for example, include amicroprocessor, microcontroller, digital signal processor, fieldprogrammable gate array, or application specific integrated circuit.

The ED 1810 also includes at least one transceiver 1802. The transceiver1802 is configured to modulate data or other content for transmission byat least one antenna or NIC (Network Interface Controller) 1804. Thetransceiver 1802 is also configured to demodulate data or other contentreceived by the at least one antenna 1804. Each transceiver 1802includes any suitable structure for generating signals for wireless orwired transmission or processing signals received wirelessly or by wire.Each antenna 1804 includes any suitable structure for transmitting orreceiving wireless or wired signals. One or multiple transceivers 1802could be used in the ED 1810, and one or multiple antennas 1804 could beused in the ED 1810. Although shown as a single functional unit, atransceiver 1802 could also be implemented using at least onetransmitter and at least one separate receiver.

The ED 1810 further includes one or more input/output devices 1806 orinterfaces (such as a wired interface to the Internet 1750). Theinput/output devices 1806 facilitate interaction with a user or otherdevices (network communications) in the network. Each input/outputdevice 1806 includes any suitable structure for providing information toor receiving information from a user, such as a speaker, microphone,keypad, keyboard, display, or touch screen, including network interfacecommunications.

In addition, the ED 1810 includes at least one memory 1808. The memory1808 stores instructions and data used, generated, or collected by theED 1810. For example, the memory 1808 could store software or firmwareinstructions executed by the processing unit(s) 1800 and data used toreduce or eliminate interference in incoming signals. Each memory 1808includes any suitable volatile or non-volatile storage and retrievaldevice(s). Any suitable type of memory may be used, such as randomaccess memory (RAM), read only memory (ROM), hard disk, optical disc,subscriber identity module (SIM) card, memory stick, secure digital (SD)memory card, and the like.

As shown in FIG. 18B, the base station 1870 includes at least oneprocessing unit 1850, at least one transceiver 1852, which includesfunctionality for a transmitter and a receiver, one or more antennas1856, at least one memory 1858, and one or more input/output devices orinterfaces 1866. A scheduler, which would be understood by one skilledin the art, is coupled to the processing unit 1850. The scheduler couldbe included within or operated separately from the base station 1870.The processing unit 1850 implements various processing operations of thebase station 1870, such as signal coding, data processing, powercontrol, input/output processing, or any other functionality. Theprocessing unit 1850 can also support the methods and teachingsdescribed in more detail above. Each processing unit 1850 includes anysuitable processing or computing device configured to perform one ormore operations. Each processing unit 1850 could, for example, include amicroprocessor, microcontroller, digital signal processor, fieldprogrammable gate array, or application specific integrated circuit.

Each transceiver 1852 includes any suitable structure for generatingsignals for wireless or wired transmission to one or more EDs or otherdevices. Each transceiver 1852 further includes any suitable structurefor processing signals received wirelessly or by wire from one or moreEDs or other devices. Although shown combined as a transceiver 1852, atransmitter and a receiver could be separate components. Each antenna1856 includes any suitable structure for transmitting or receivingwireless or wired signals. While a common antenna 1856 is shown here asbeing coupled to the transceiver 1852, one or more antennas 1856 couldbe coupled to the transceiver(s) 1852, allowing separate antennas 1856to be coupled to the transmitter and the receiver if equipped asseparate components. Each memory 1858 includes any suitable volatile ornon-volatile storage and retrieval device(s). Each input/output device1866 facilitates interaction with a user or other devices (networkcommunications) in the network. Each input/output device 1866 includesany suitable structure for providing information to orreceiving/providing information from a user, including network interfacecommunications.

FIG. 19 is a block diagram of a computing system 1900 that may be usedfor implementing the devices and methods disclosed herein. For example,the computing system can be any entity of UE, access network (AN),mobility management (MM), session management (SM), user plane gateway(UPGW), or access stratum (AS). Specific devices may utilize all of thecomponents shown or only a subset of the components, and levels ofintegration may vary from device to device. Furthermore, a device maycontain multiple instances of a component, such as multiple processingunits, processors, memories, transmitters, receivers, etc. The computingsystem 1900 includes a processing unit 1902. The processing unitincludes a central processing unit (CPU) 1914, memory 1908, and mayfurther include a mass storage device 1904, a video adapter 1910, and anI/O interface 1912 connected to a bus 1920.

The bus 1920 may be one or more of any type of several bus architecturesincluding a memory bus or memory controller, a peripheral bus, or avideo bus. The CPU 1914 may comprise any type of electronic dataprocessor. The memory 1908 may comprise any type of non-transitorysystem memory such as static random access memory (SRAM), dynamic randomaccess memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM),or a combination thereof. In an embodiment, the memory 1908 may includeROM for use at boot-up, and DRAM for program and data storage for usewhile executing programs.

The mass storage 1904 may comprise any type of non-transitory storagedevice configured to store data, programs, and other information and tomake the data, programs, and other information accessible via the bus1920. The mass storage 1904 may comprise, for example, one or more of asolid state drive, hard disk drive, a magnetic disk drive, or an opticaldisk drive.

The video adapter 1910 and the I/O interface 1912 provide interfaces tocouple external input and output devices to the processing unit 1902. Asillustrated, examples of input and output devices include a display 1918coupled to the video adapter 1910 and a mouse, keyboard, or printer 1916coupled to the I/O interface 1912. Other devices may be coupled to theprocessing unit 1902, and additional or fewer interface cards may beutilized. For example, a serial interface such as Universal Serial Bus(USB) (not shown) may be used to provide an interface for an externaldevice.

The processing unit 1902 also includes one or more network interfaces1906, which may comprise wired links, such as an Ethernet cable, orwireless links to access nodes or different networks. The networkinterfaces 1906 allow the processing unit 1902 to communicate withremote units via the networks. For example, the network interfaces 1906may provide wireless communication via one or more transmitters/transmitantennas and one or more receivers/receive antennas. In an embodiment,the processing unit 1902 is coupled to a local-area network 1922 or awide-area network for data processing and communications with remotedevices, such as other processing units, the Internet, or remote storagefacilities.

It should be appreciated that one or more steps of the embodimentmethods provided herein may be performed by corresponding units ormodules. For example, a signal may be transmitted by a transmitting unitor a transmitting module. A signal may be received by a receiving unitor a receiving module. A signal may be processed by a processing unit ora processing module. Other steps may be performed by a detecting unit ormodule, a communicating unit or module, a processing unit or module, adecoding unit or module, or a combining unit or module. The respectiveunits or modules may be hardware, software, or a combination thereof.For instance, one or more of the units or modules may be an integratedcircuit, such as field programmable gate arrays (FPGAs) orapplication-specific integrated circuits (ASICs).

Although the present disclosure and its advantages have been describedin detail, it should be understood that various changes, substitutionsand alterations can be made herein without departing from the spirit andscope of the disclosure as defined by the appended claims.

What is claimed is:
 1. A method comprising: transmitting, to a userequipment (UE), a first assignment for a first transmission in a firstnetwork resource; transmitting, to the UE, a second assignment for asecond transmission in a second network resource, wherein the firstnetwork resource and the second network resource are associated withdifferent transmission/receiving points (TRPs) of an access node, andthe first assignment and the second assignment are in a single downlinkcontrol information (DCI); transmitting, to the UE, an indicationincluding a semi-static configuration indicating that the firsttransmission and the second transmission are for a same transport block(TB); and communicating, with the UE, at least one transmission of thefirst transmission or the second transmission in at least one respectivenetwork resource of the first network resource or the second networkresource.
 2. The method of claim 1, wherein the communicating the atleast one transmission comprises: receiving, from the UE, the at leastone transmission.
 3. The method of claim 1, wherein the communicatingthe at least one transmission comprises: transmitting, to the UE, the atleast one transmission.
 4. The method of claim 1, wherein the firstnetwork resource and the second network resource include at least one ofa frequency resource, a time resource, a code resource, a spatialresource, a carrier, a component carrier, or a bandwidth part (BWP). 5.The method of claim 1, wherein the indication is the semi-staticconfiguration.
 6. The method of claim 1, wherein the indication is acombination of the semi-static configuration and dynamic signaling. 7.An apparatus comprising: one or more processors in communication with anon-transitory memory storage storing instructions, wherein the one ormore processors execute the instructions to cause the apparatus to:transmit, to a user equipment (UE), a first assignment for a firsttransmission in a first network resource; transmit, to the UE, a secondassignment for a second transmission in a second network resource,wherein the first network resource and the second network resource areassociated with different transmission/receiving points (TRPs) of anaccess node, and the first assignment and the second assignment are in asingle downlink control information (DCI), the access node comprisingthe apparatus; transmit, to the UE, an indication including asemi-static configuration indicating that the first transmission and thesecond transmission are for a same transport block (TB); andcommunicate, with the UE, at least one transmission of the firsttransmission or the second transmission in at least one respectivenetwork resource of the first network resource or the second networkresource.
 8. The apparatus of claim 7, wherein the instructions to causethe apparatus to communicate the at least one transmission compriseinstructions to cause the apparatus to: receive, from the UE, the atleast one transmission.
 9. The apparatus of claim 7, wherein theinstructions to cause the apparatus to communicate the at least onetransmission comprise instructions to cause the apparatus to: transmit,to the UE, the at least one transmission.
 10. The apparatus of claim 7,wherein the first network resource and the second network resourceinclude at least one of a frequency resource, a time resource, a coderesource, a spatial resource, a carrier, a component carrier, or abandwidth part (BWP).
 11. The apparatus of claim 7, wherein theindication is the semi-static configuration.
 12. The apparatus of claim7, wherein the indication is a combination of the semi-staticconfiguration and dynamic signaling.
 13. An apparatus comprising: one ormore processors in communication with a non-transitory memory storagestoring instructions, wherein the one or more processors execute theinstructions to cause the apparatus to: receive a first assignment for afirst transmission in a first network resource; receive a secondassignment for a second transmission in a second network resource,wherein the first network resource and the second network resource areassociated with different transmission/receiving points (TRPs) of anaccess node, and the first assignment and the second assignment are in asingle downlink control information (DCI); detect an indicationincluding a semi-static configuration indicating that the firsttransmission and the second transmission are for a same transport block(TB); and communicate, with the access node, at least one transmissionof the first transmission or the second transmission in at least onerespective network resource of the first network resource and the secondnetwork resource.
 14. The apparatus of claim 13, wherein theinstructions to cause the apparatus to communicate the at least onetransmission comprise instructions to cause the apparatus to: receivethe at least one transmission from the access node.
 15. The apparatus ofclaim 13, wherein the instructions to cause the apparatus to communicatethe at least one transmission comprise instructions to cause theapparatus to: transmit the at least one transmission to the access node.16. The apparatus of claim 13, wherein the first network resource andthe second network resource include at least one of a frequencyresource, a time resource, a code resource, a spatial resource, acarrier, a component carrier, or a bandwidth part (BWP).
 17. Theapparatus of claim 13, wherein the indication is the semi-staticconfiguration.
 18. The apparatus of claim 13, wherein the indication isa combination of the semi-static configuration and dynamic signaling.